docs(aws-serverless): update LMI skill for region expansion and scheduled scaling#201
Merged
krokoko merged 8 commits intoJun 30, 2026
Merged
Conversation
…uled scaling - Region availability: now all commercial AWS Regions except Israel (Tel Aviv), Middle East (Bahrain), Middle East (UAE), and Asia Pacific (Auckland); update Unsupported Region handling. - Scheduled scaling: document EventBridge Scheduler-based scheduled scaling of Min/Max execution environments for predictable traffic (SKILL.md, configuration-guide.md, infrastructure-setup.md).
sbbhimji
requested review from
a team,
krokoko,
scottschreckengaust and
theagenticguy
Contributor
|
@sbbhimji thanks ! Don't forget to upgrade the version of the plugin in the multiple files |
- Add formulas for deriving MaxConcurrency, MemorySize, and
MinExecutionEnvironments
from Lambda Insights metrics (cpu_total_time, memory_utilization,
ConcurrentExecutions)
- Add fallback guidance when Lambda Insights is not available
- Add Lambda Insights enablement instructions
- Fix default memory-to-vCPU ratio from 4:1 to 2:1 (matches public
docs and CDK defaults)
- Fix weighted alias traffic shifting claim (not currently supported
for LMI)
- Add testing phase troubleshooting guidance (CPUThrottles,
MemoryThrottles,
DiskThrottles, ConcurrencyThrottles, low CPU utilization)
- Update Best Practices to align with corrected defaults
… formatting Follow-up to the migration-assessment PR: correct the broken Lambda Insights versions doc URL and add blank lines around lists in troubleshooting.md so dprint/markdownlint pass.
Region expansion + scheduled scaling + migration-assessment guidance are backward-compatible feature additions to the LMI skill (minor bump). Updated plugin.json, .codex-plugin/plugin.json, and marketplace.json.
Contributor
|
@bfreiberg @jaycol-aws could you please have a look ? thanks ! |
|
Taking a look |
|
Looks good for the most part. Only thing I would call out is can exceed the 32GB max as written, should wrap in another min statement so it cannot exceed 32GB. |
Address review feedback: the MemorySize derivation had a floor (max with 2048) but no ceiling, so it could exceed the 32 GB LMI limit. Wrap in min(32768, ...) to cap at the maximum.
Contributor
Author
Good catch. just fixed it |
krokoko
previously approved these changes
Jun 30, 2026
main already advanced aws-serverless to 1.2.0 via the aws-lambda-microvms skill (awslabs#202). Bump this PR to 1.3.0 to avoid a duplicate-version collision; the LMI region/scheduled-scaling additions are backward-compatible features (minor bump from 1.2.0).
krokoko
approved these changes
Jun 30, 2026
jaycol-aws
approved these changes
Jun 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Updates the
aws-lambda-managed-instancesskill (in theaws-serverlessplugin) for two recent Lambda Managed Instances launches:MinExecutionEnvironments/MaxExecutionEnvironmentson a one-time or recurring schedule for predictable traffic (scale up before peak, scale down or to zero when idle).Files changed
SKILL.md: regional availability + unsupported-Region scenario;scheduled scalingtrigger andscheduled-scalingtag in frontmatter; scheduled-scaling note in Step 3; two Operations best practices; reference-file pointers; Scaling docs link in Resources.references/configuration-guide.md: new "Scheduled Scaling (Predictable Traffic)" section — behavior notes (still scales on CPU/concurrency between bounds;Min=Max=0deactivates and needs explicit reactivation) and a common-patterns table.references/infrastructure-setup.md: new "Scheduled Scaling (EventBridge Scheduler)" section — scheduler IAM trust/permissions policies,create-scheduleexamples targeting thePutFunctionScalingConfiguniversal target, and a manualput-function-scaling-configoverride.Testing
dprint check— cleanmarkdownlint-cli2(incl. custom skill-length + frontmatter rules) — 0 errorslint:cross-refs— 0 errorsvalidate:refs— 0 broken linksvalidate:size— SKILL.md 225 lines / 1566 words, description 626 chars (all under limits)Documentation-only change; content verified against the LMI scaling documentation. Uses placeholder identifiers (
<account-id>) only.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the project license.